Recommended Uses
CygNet recommends using the VHS Import/Export utility in the ways described below.
| From (Source) | To (Destination) | Use To |
|---|---|---|
|
Value History Service |
Value History Service |
Transfer data from one VHS to another. The source service can be on a different domain from the destination service. Note: You can use this method to migrate data from a VHS legacy datastore (.dat files) to a ESE-based datastore (history.edb and \txlogs folder). See Data Storage for more information. |
|
Value History Service (Legacy) |
Value History Service (Legacy) |
Create .dat files for transfer or backup. All .dat files are required. |
|
Value History Service (ESE) |
Value History Service (ESE) |
Migrate data from a live VHS running an ESE-based datastore to another ESE-based datastore. All data files are required (history.edb and \txlogs folder). |
|
Value History Service |
CSV file |
Export data for review purposes. |
|
CSV File |
Value History Service |
Import non-CygNet data (must be in valid format). If a point does not already exist in the destination VHS, then the point will only be added if the file contains both its Point ID and Long ID. |
|
Offline datastore |
Value History Service (Legacy) |
Import data from an offline datastore to a legacy datastore. All .dat files are required. See Data Storage for more information. |
|
Offline datastore |
Value History Service (ESE) |
Import data from an offline datastore to a live ESE-based service. All data files are required (history.edb and \txlogs folder). |
Note: The VHS Import/Export utility can be used to import a thinned data file into a newly created history.edb datastore, thus eliminating wasted disk space.
Other Resources
- See the CygNet Studio sample screen, CygNet\Clients\CStudio\Screens\Examples\TransferPointHistory.csf, which invokes multiple instances of the VhsImportExport utility to more quickly transfer a large amount of VHS data from one historian service to another.
